@Ilya-Mordasov said in No wireless: yes, that seems to be the problem, because only the wireless is not working, I tried i2c and spidev, everything is fine. Yeah, only the wifi driver relies on the data in the factory partition. So it makes sense that everything else works. Do I only need to know the factory MAC address or do I need to have access to the whole chip? My guess is that you'll need a whole new copy of the factory partition - it looks like the wifi driver in openwrt 22.03 has a workaround for invalid MAC addresses but still crashes because of the rest of the invalid configuration. Do I need to connect wires to the chip? No need to connect wires, you can do it from Linux. And how can I extract the factory partition from the live chip? To copy the factory partition from one device to another, it's actually super similar to the steps in the post linked by @crispyoz: @Lazar-Demin said in Contradiction in Omega2 Device MAC Address Allocation: install the xxd package dump the factory partition to hex: xxd /dev/mtd2 > factory.hex create a backup just in case edit the two mac addresses (can use vi) convert the edited hex file to binary: xxd -r factory-new.hex > factory.bin write the binary file to the factory partition: mtd -r write factory.bin factory Do steps 1 to 5 on a working device, and step 6 on your current device. (You'll probably need to reinstall whichever firmware was successfully booting on your current device in order to get to Linux)

@Lazar-Demin Unfortunately, both ways you've suggested don't work to me, I don't have ethernet port, I use my custom shield, and I was trying to flash it via USB, but according to google I have old U-Boot 1.1.3 and Onion Omega2 UBoot Version: 4.3.0.3 and when I try to flash fw from the usb I get timeout error (found that it was solved in later versions) I use the next steps to flash my omega2: start command line tool attach usb and copy openwrt-initramfs image to 0x81000000 erase linux bootm 0x81000000 so when the device is running I connect to it via ssh and write omega2-0.3.3-b256 fw 5. cat omega2-v0.3.3-b256.bin | ssh root@192.168.1.1 mtd write - firmware These steps are ok for 0.1.10-b160 and openwrt-22.05.02 firmwares, but not for the latests openwrt is ok for general purposes (wifi connection, msc, etc), but it has a problems with interfaces, such as spi, i2c, gpio in general, so then omega2-0.1.10 is ok for that

UPDATE Realized I can connect via serial super easy on mac - this is the result: https://pastebin.com/raw/ThHYgeYw I entered firstboot -y; sync; reboot and now its AP popping up again. did the wifi setup via ssh this time. Seems to all work now... I'll leave this here, maybe someone finds it useful. Some more info here is that the serial drivers offered for mac are crashing on M1 big sur but are apparently not even needed, the omega shows up as /dev/tty.usbserial-0001

After having looked at the issue we realized that the issue is in the install file that we used. We mistakenly used the file for an Omega2+ install while using and Omega2 module. The two FW files are exactly the same in terms of byte size, however the content is quite different and results in the module not being able to boot properly. Here is an image of the log thinking it is an Omega2+ module despite not being one:

@Russell-Pirie "...will they all fit??...." You'd need to be specific as to what they are and how they are configured in order to answer that. I'm not sure you need to rewrite a bluetooth driver, most users would utilise "Bluez" package for bluetooth, perhaps take a look at that package and see if it meets your requirements, here's a link to the package: https://openwrt.org/docs/guide-user/hardware/bluetooth/usb.bluetooth I flash my devices using a bash script (well ash), it just connects to the device(s) using ipv6, uploads the firmware and then ssh's into the device and execute the firmware upgrade. You could tweak my script a bit to make it handle multiple devices at once. I did about 40 of them today using my exiting script, one by one while I was eating lunch and watching the news. My script is here: https://community.onion.io/topic/4483/script-to-deploy-firmware-to-device-using-ethernet-ipv6 The other option is to boot into u-boot and flash from USB.

@jonty I can see you are getting a read timeout, add the -v parameter and check /tmp/pip-log.txt

@jonty clean up your file system to give yourself a little more space.

@crispyoz Interesting. I got the Omega2 so I'll have to make do with a single USB drive.

@jonty No. The wireless Arduino IDE method outlined in our documentation has worked consistently since the launch of the Arduino Dock 2 back in 2016. In @Noniono's case, using a programmer is meant to test the MCU. It isn't responding to the Omega. If it also doesn't respond to the programmer, then we know the MCU has somehow gotten into a bad state or has been damaged.

See our documentation article on opkg for more info: http://docs.onion.io/omega2-docs/using-opkg.html

Hey guys. I have the latest firmware version 0.3.2 (b233) on my Omega2 and also increased my storage using external drive, but still face the same issue. Could anyone help? )

@Denis-Ber The easy way to understand how to use UCI is try this: uci show wireless Look at the result and you should see the wifi password something like this: wireless.sta.key='b840e8634d3d81e89e442cdbc' Then use the command: uci set wireless.sta.key='your new key' uci commit wireless service network restart

I've never tried it, but you could possibly use a USB to Ethernet adaptor to add additional Ethernet Ports.

@crispyoz Thanks, that helped. I am very grateful to you.

@cory-callcott hi I can't remember how much as I ended up using a USB drive to expand the storage but u can use the command 'df -h' before and after to find out

@Christopher-Pyzik Unlike some very popular boards (eg RPi) I don't think there are many (if any? - others can shout at me if I'm wrong 3rd party commercial 'hats'/expansion boards. Some contributors have built their own expansions for their own needs (browse through the Projects forum to see what others are doing), but as for commercial boards specifically targeted at the Onion devices, I believe that the Onion store will be your likely source. Having said that, the point of the devices (IMHO) are to spark your own ingenuity and get you to explore and build your own projects and if that means taking it to the board level, then that is what you should do, as have others. I see the commercial expansions from Onion as tools for prototyping and in some cases, all that is necessary to realise your own project. But the flexibility is there for you to do with them as you choose - or not even use them at all and instead design your own.

One more thing I can actually get 1,000,000 baud working. The problem was the error from the microcontroller was getting too high even in its high speed mode as it just did not have the resolution for super high baud rates (the micro only runs at 24Mhz). When the baud divisor value on the micro gets into the single digits the step between each digit is quite large in terms of baud rate, so just happened to get lucky at 430600 and 600000 as they coincided with low error values. I had not realized at the time why these worked, but it is obvious now. So am happy with 1MBaud. Quite a bump up from 115200 I would say.